Skip to content

Conversation

mariammorgan
Copy link
Contributor

adding this part
When a sender is added to the block list in the email junk configuration, any future emails from that sender will be classified as spam. The email header will include X-Forefront-Antispam-Report: SFV:BLK, indicating the sender is blocked.

The action defined in the anti-spam policy for spam detection will then be applied:

If the configured action is junk, the email will be delivered to the Junk Email folder. If the action is quarantine, the email will be quarantined. 📌 Recommended Action by Microsoft: Set the spam action to junk. 🔗 https://learn.microsoft.com/en-us/defender-office-365/recommended-settings-for-eop-and-office365

Because cx has spam action quarantine and come back asking why mail quarantine and sender is in block list of mail junk configuration so it need to be cleared for them that depend on spam action and our documentation mentioned junk as standard action for spam mail is junk not quarantine

adding this part 
When a sender is added to the block list in the email junk configuration, any future emails from that sender will be classified as spam. The email header will include X-Forefront-Antispam-Report: SFV:BLK, indicating the sender is blocked.

The action defined in the anti-spam policy for spam detection will then be applied:

If the configured action is junk, the email will be delivered to the Junk Email folder.
If the action is quarantine, the email will be quarantined.
📌 Recommended Action by Microsoft: Set the spam action to junk.
🔗 https://learn.microsoft.com/en-us/defender-office-365/recommended-settings-for-eop-and-office365


Because cx has spam action quarantine and come back asking why mail quarantine and sender is in block list of mail junk configuration so it need to be cleared for them that depend on spam action and our documentation mentioned junk as standard action for spam mail is junk not quarantine
Copy link
Contributor

Learn Build status updates of commit 07baf26:

⚠️ Validation status: warnings

File Status Preview URL Details
defender-office-365/configure-junk-email-settings-on-exo-mailboxes.md ⚠️Warning Details

defender-office-365/configure-junk-email-settings-on-exo-mailboxes.md

  • Line 40, Column 4: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/defender-office-365/recommended-settings-for-eop-and-office365' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
  • Line 40, Column 4: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/defender-office-365/recommended-settings-for-eop-and-office365' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

Copy link
Contributor

Learn Build status updates of commit e539cdf:

✅ Validation status: passed

File Status Preview URL Details
defender-office-365/configure-junk-email-settings-on-exo-mailboxes.md ✅Succeeded

For more details, please refer to the build report.

Copy link
Contributor

Learn Build status updates of commit 14bf634:

✅ Validation status: passed

File Status Preview URL Details
defender-office-365/configure-junk-email-settings-on-exo-mailboxes.md ✅Succeeded

For more details, please refer to the build report.

@chrisda chrisda merged commit 4919a5a into MicrosoftDocs:public Jul 31, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants